Pest control system and method of operating same

ABSTRACT

A pest control device comprising a capacitive sensor array including a plurality of sensor pads, the capacitive sensor array being configured to generate an electrical output signal indicating the state of each sensor pad, and an electronic controller electrically connected to the capacitive sensor array, the electronic controller including a processor and a memory including a plurality of instructions, which, when executed by the processor, causes the processor to: receive the electrical output signals from the capacitive sensor array, determine a measured capacitance value for each sensor pad based on each electrical output signal, calculate a baseline for each sensor pad based on the measured capacitance value of the sensor pad, determine whether a difference between the measured capacitance value of at least one sensor pad and its corresponding baseline exceeds a first predetermined threshold, update a counter when the first predetermined threshold is exceeded, and record an event indicative of a presence of a pest when the counter exceeds a predetermined limit.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of U.S. application Ser.No. 16/653,318, entitled “PEST CONTROL SYSTEM AND METHOD OF OPERATINGSAME,” which was filed on Oct. 15, 2019, and which is a continuation ofU.S. application Ser. No. 16/553,295, entitled “PEST CONTROL SYSTEM ANDMETHOD OF OPERATING SAME,” which was filed on Aug. 28, 2019 and whichissued on Feb. 4, 2020 as U.S. Pat. No. 10,548,308, and which is acontinuation application of U.S. application Ser. No. 15/524,444,entitled “PEST CONTROL SYSTEM AND METHOD OF OPERATING SAME,” which wasfiled on May 4, 2017, and which is a national stage entry under 35 USC §371(b) of PCT International Application No. PCT/US2015/058756, filedNov. 3, 2015, and claims the benefit of and priority to U.S. PatentApplication No. 62/074,913 filed Nov. 4, 2014 and entitled “CAPACITIVESENSING HARDWARE AND SOFTWARE IN THE DETECTION OF PESTS,” U.S. PatentApplication No. 62/236,519 filed Oct. 2, 2015 and entitled “PEST CONTROLDEVICE AND METHOD OF MONITORING POSITION OF SAME,” and U.S. PatentApplication No. 62/243,410 filed on Oct. 19, 2015 and entitled “PESTCONTROL SYSTEM AND METHOD OF OPERATING SAME.” Each of those applicationsis expressly incorporated herein by reference.

TECHNICAL FIELD

The present disclosure relates generally to devices for controllingpests, and, more specifically, to devices for monitoring andcommunicating the presence of pests, and eliminating pests.

BACKGROUND

The detection and removal of pests from areas occupied by humans,livestock, crops, and other pest-attracting areas has long been achallenge. Pests of frequent concern include various types of insectsand rodents. Subterranean termites are a particularly troublesome typeof pest with the potential to cause severe damage to wooden structures.Likewise, other insects, such as bedbugs, are problematic. Additionally,rodent control is often challenging. Various schemes have been proposedto eliminate these and certain other harmful pests. Some of thoseschemes use one or more stations, which must be periodically checked byservice personnel. Similarly, rodent traps in residential and commercialsettings need to be routinely checked by service personnel.

SUMMARY

According to one aspect of the disclosure, a pest control device isdisclosed. The pest control device comprises a capacitive sensor arrayincluding a plurality of sensor pads, and an electronic controllerelectrically connected to the capacitive sensor array. The capacitivesensor array is configured to generate an electrical output signalindicating the state of each sensor pad. The electronic controllerincludes a processor and a memory including a plurality of instructions,which, when executed by the processor, causes the processor to receivethe electrical output signals from the capacitive sensor array,determine a measured capacitance value for each sensor pad based on eachelectrical output signal, calculate a baseline for each sensor pad basedon the measured capacitance value of the sensor pad, determine whether adifference between the measured capacitance value of at least one sensorpad and its corresponding baseline exceeds a first predeterminedthreshold, update a counter when the first predetermined threshold isexceeded, and record an event indicative of a presence of a pest whenthe counter exceeds a predetermined limit.

In some embodiments, the plurality of instructions further cause theprocessor to calculate each baseline using the following equations:

${A({new})} = {{A({old})} - {{A({old})}*\left( \frac{Kf}{2^{16}} \right)} + {Cmeas}}$${Baseline} = {{A({new})}*\left( \frac{Kf}{2^{16}} \right)}$

“Kf” may be a parameter stored in a memory device of the electroniccontroller, “Cmeas” may be the measured capacitance value correspondingto the electrical output signal of one sensor pad, and “A(old)” may be avariable stored in memory. In some embodiments, the electroniccontroller may be configured to receive values of Kf from a remotesystem.

In some embodiments, the electronic controller is configured to record asecond event when the electrical output signals indicate a presence of ahuman.

In some embodiments, the plurality of instructions further cause theprocessor to determine a sequence of sensor pad contacts based on theelectrical output signals, compare the sequence of sensor pad contactsto a predetermined sequence, and record the second event when thesequence of sensor pad contacts matches the predetermined sequence. Thepest control device may include a first visual indicator electricallyconnected to the electronic controller, and the electronic controllermay be configured to energize the first visual indicator when thesequence of sensor pad contacts matches the predetermined sequence.

In some embodiments, the pest control device may include a second visualindicator electrically connected to the electronic controller, and theelectronic controller may be configured to energize the first visualindicator and the second visual indicator when the electrical outputsignals indicate the presence of the pest.

In some embodiments, the plurality of instructions further cause theprocessor to determine whether the difference between the measuredcapacitance value of at least one sensor pad exceeds a secondpredetermined threshold, and update the counter when the difference isless than the second predetermined threshold. In some embodiments, theplurality of instructions further cause the processor to determine asequence of sensor pad contacts based on the electrical output signalswhen the difference is greater than the second predetermined threshold,compare the sequence of sensor pad contacts to a predetermined sequence,and record the second event when the sequence of sensor pad contactsmatches the predetermined sequence.

In some embodiments, the pest control device may include a positionsensor operable to generate an electrical output signal indicative ofmovement of the pest control device. In some embodiments, the pluralityof instructions cause the processor to receive the electrical outputsignal from the position sensor, determine, based on the electricaloutput signals, whether the pest control device has been in a firstposition for a predetermined period of time, determine, based on theelectrical output signals, a deflection angle of the pest control devicewhen the pest control device has been in the first position for thepredetermined period of time, compare the deflection angle of the pestcontrol device to a predetermined angular threshold, and generate anoutput signal when the deflection angle is greater than thepredetermined angular threshold.

According to another aspect, a method of monitoring for pests isdisclosed. The method includes generating an electrical output signalfrom a capacitive sensor array, receiving the electrical output signalfrom the capacitive sensor array, determining a measured capacitancevalue based on the electrical output signal, calculating a baseline foreach sensor pad based on the measured capacitance value for the sensorpad, determining whether a difference between the measured capacitancevalue of at least one sensor pad and its corresponding baseline exceedsa first predetermined threshold, updating a counter when the firstpredetermined threshold is exceeded, and recording an event indicativeof a presence of a pest when the counter exceeds a predetermined limit.

In some embodiments, the plurality of instructions further cause theprocessor to calculate each baseline using the following equations:

${A({new})} = {{A({old})} - {{A({old})}*\left( \frac{Kf}{2^{16}} \right)} + {Cmeas}}$${Baseline} = {{A({new})}*\left( \frac{Kf}{2^{16}} \right)}$

“Kf” may be a parameter stored in a memory device of the electroniccontroller, “Cmeas” may be the measured capacitance value correspondingto the electrical output signal of one sensor pad, and “A(old)” may be avariable stored in memory.

In some embodiments, the method may include recording a second eventwhen the electrical output signals indicate a presence of a human.

In some embodiments, the method may include determining whether thedifference between the measured capacitance value of at least one sensorpad and its corresponding baseline exceeds a second predeterminedthreshold, and updating the counter when the difference is less than thesecond predetermined threshold. The method may include determining asequence of sensor pad contacts based on the electrical output signalswhen the difference is greater than the second predetermined threshold,and comparing the sequence of sensor pad contacts to a predeterminedsequence. In some embodiments, recording the second event may includedetermining the sequence of sensor pad contacts matches thepredetermined sequence.

According to another aspect, a pest control system is disclosed. Thesystem includes a station including a chamber sized to receive a pest,and a control device coupled to the station. The control device includesa capacitive sensor array including a plurality of sensor pads, thecapacitive sensor array being configured to generate an electricaloutput signal indicating the state of each sensor pad, and an electroniccontroller electrically connected to the capacitive sensor array. Theelectronic controller being configured to receive the electrical outputsignals from the capacitive sensor array, and record a first event whenat least one of the electrical output signals indicates a presence of apest. In some embodiments, the electronic controller is configured torecord a second event when at least one of the electrical output signalsindicates a presence of a human.

In some embodiments, the system includes bait positioned in the chamberof the station. Additionally, in some embodiments, the control devicemay further include a position sensor operable to generate an electricaloutput signal indicative of movement of the station. The electroniccontroller may be configured to record a movement event based on theelectrical output signal from the position sensor.

In some embodiments, the control device may further include atemperature sensor.

According to another aspect, a pest control system is disclosed. Thesystem includes a pest control device. The pest control device includesa sensor array operable to generate electrical output signals indicativeof a presence of a pest, an orientation sensor operable to generate aplurality of electrical output signals indicative of the position of thepest control device, and an electronic controller electrically connectedto the sensor array and the position sensor. The electronic controllerfurther includes a processor and a memory including a plurality ofinstructions, which, when executed by the processor, causes theprocessor to: receive the electrical output signal from the positionsensor, determine, based on the electrical output signals, whether thepest control device has been in a first position for a predeterminedperiod of time, determine, based on the electrical output signals, adeflection angle of the pest control device when the pest control devicehas been in the first position for the predetermined period of time,compare the deflection angle of the pest control device to apredetermined angular threshold, and generate an output signal when thedeflection angle is greater than the predetermined angular threshold.

In some embodiments, the position sensor may be an accelerometer. Insome embodiments, the pest control system further comprises a pest trapdevice, and the pest control device is configured to be coupled to thepest trap device.

In some embodiments, the pest control device further comprises an outercasing and a support leg pivotally coupled to the outer casing, thesupport leg including a panel sized to be positioned below the pest trapdevice. In some embodiments, the support leg may be coupled to the outercasing via a mounting arm of a plurality of mounting arms, the pluralityof mounting arms extending along a sidewall of the outer casing.

In some embodiments, the pest trap device includes a hinged bar operableto pivot about an axis. In some embodiments, the pest control device maycomprise an outer casing and at least one clip operable to engage thehinged bar such that the pest control device is moved with the hingedbar when the hinged bar is pivoted about the axis.

In some embodiments, the pest trap device further comprises a base and apivoting member pivotally coupled to the base, and the pest controldevice is mounted on a top surface of the pivoting member.

According to another aspect, a pest control system is disclosed. Thesystem includes a pest control device and a pest control device. Thepest control device is configured to be coupled to the pest trap device.The pest control device includes an electronic controller electricallyconnected to the capacitive sensor array. The electronic controller isfurther configured to receive the electrical output signals from thecapacitive sensor array, determine a measured capacitance value for eachsensor pad based on each electrical output signal, calculate baselinesfor the sensor pads based on the measured capacitance values, determinewhether a difference between the measured capacitance value of at leastone sensor pad and its corresponding baseline exceeds a firstpredetermined threshold, update a counter when the first predeterminedthreshold is exceeded, and record an event indicative of a presence of apest when the counter exceeds a predetermined limit.

In some embodiments, the pest control device comprises a capacitivesensor array including a plurality of sensor pads. The capacitive sensorarray may be configured to generate an electrical output signalindicating the state of each sensor pad. In some embodiments, theelectronic controller may be configured to receive the electrical outputsignals from the capacitive sensor array, and record a first event whenat least one of the electrical output signals indicates a presence of apest.

In some embodiments, the pest control device further comprises an outercasing and a support leg pivotally coupled to the outer casing, thesupport leg including a panel sized to be positioned below the pest trapdevice. In some embodiments, the pest trap device may include a hingedbar operable to pivot about an axis. In some embodiments, the pestcontrol device may comprise an outer casing and at least one clipoperable to engage the hinged bar such that the pest control device ismoved with the hinged bar when the hinged bar is pivoted about the axis.

In some embodiments, the support leg is coupled to the outer casing viaa mounting arm of a plurality of mounting arms, the plurality ofmounting arms extending along a sidewall of the outer casing.

According to another aspect, a method of monitoring for pests isdisclosed. The method includes recording a plurality of orientationvalues from an orientation sensor of a pest control device that isremovably coupled to a pest trap device, each orientation value iscomprising (x, y, z) coordinates corresponding to an orientation of thepest control device, determining whether the pest control device isstable based on the plurality of orientation values, determining anorientation of the pest control device when the pest control device isstable, determining a trap condition of the pest trap device based onthe orientation of the pest control device, and transmitting the trapcondition to a remote system to determine a trap status of the pest trapdevice.

In some embodiments, recording the plurality of orientation valuesfurther comprises recording each orientation value from the orientationsensor after a predetermined time interval has lapsed until apredetermined number of the orientation values are recorded.

In some embodiments, the predetermined number of the orientation valuesis at least 8 orientation values.

In some embodiments, determining whether the pest control device isstable based on the plurality of orientation values comprisesdetermining maximum orientation values and minimum orientation valuesfrom the plurality of orientation values for each of the (x, y, z)coordinates, determining differences between the maximum orientationvalues and the minimum orientation values for each of the (x, y, z)coordinates of the plurality of orientation values, determining whetherall of the differences are less than or equal to a first set ofpredetermined thresholds, determining average orientation value for eachof the (x, y, z) coordinates of the plurality of orientation values whenall of the differences are less than or equal to the first set ofpredetermined thresholds, and storing the (x, y, z) coordinates of theaverage orientation value with a new stable orientation value toindicate that the pest control device is stable.

In some embodiments, determining whether the pest control device isstable based on the plurality of orientation values comprisesdetermining maximum orientation values and minimum orientation valuesfrom the plurality of orientation values for each of the (x, y, z)coordinates, determining differences between the maximum orientationvalues and the minimum orientation values for each of the (x, y, z)coordinates, determining whether a sum of the differences is less thanor equal to a first predetermined threshold, determining averageorientation values for each of the (x, y, z) coordinates from theplurality of orientation values when the sum of the differences is lessthan or equal to the first predetermined threshold, and updating theaverage orientation values to a new stable orientation coordinates.

In some embodiments, determining an orientation of the pest controldevice when the pest control device is stable comprises identifying a(x, y, z) coordinates of a previous stable orientation value,determining a deflection angle of the pest control device using the (x,y, z) coordinates of the new stable orientation value, determining thedeflection angle exceeds a second predetermined threshold, updating thetrap condition when the second predetermined threshold is exceeded, andupdating the previous stable orientation value with the new stableorientation value.

In some embodiments, calculating the deflection angle of the pestcontrol device includes using the following equations:

${DeflectionAngle} = {\cos^{- 1}\left( \frac{\left( {A_{X}*B_{X}} \right) + \left( {A_{Y}*B_{Y}} \right) + \left( {A_{Z}*B_{Z}} \right)}{\sqrt{\left( {A_{X}^{2} + A_{Y}^{2} + A_{Z}^{2}} \right)*\left( {B_{X}^{2} + B_{Y}^{2} + B_{Z}^{2}} \right)}} \right)}$

“A_(x)”, “A_(y)”, “A_(z)” are the (x, y, z) coordinates of new stableorientation value, and “B_(x)”, “B_(y)”, “B_(z)” are the (x, y, z)coordinates of previous stable orientation value.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description particularly refers to the following figures,in which:

FIG. 1 is a perspective view of a pest control system;

FIG. 2 is a cross-sectional plan view of a pest control station of FIG.1 taken along the line 2-2 in FIG. 1;

FIG. 3 is a perspective view of a pest control device of the controlstation of FIG. 2;

FIG. 4 is a block diagram schematic of the pest control device of FIG.3;

FIG. 5 is a plan view of a capacitive sensor array of the pest controldevice of FIG. 3;

FIG. 6 is a simplified flow chart of a control routine of the pestcontrol device of FIG. 3;

FIG. 7 is a simplified flow chart of one embodiment of a sub-routine ofthe control routine of FIG. 6;

FIG. 8 is a simplified flow chart of another embodiment of a sub-routineof the control routine of FIG. 6;

FIG. 9 is a simplified flow chart of a further sub-routine of thesub-routine of FIG. 8;

FIG. 10 is a simplified flow chart of another embodiment of asub-routine of the control routine of FIG. 6;

FIGS. 11a and 11b are illustrations of a simplified flow chart of afurther sub-routine of the sub-routine of FIG. 10; and

FIG. 12 is a perspective view of another embodiment of a pest controlsystem including another embodiment of a pest control device and a pesttrap device;

FIG. 13 is a top perspective view of a pest control device of FIG. 12;

FIG. 14 is a rear perspective view of a support leg of a pest controldevice of FIG. 12;

FIG. 15 is a side elevation view of the support leg of the pest controldevice of FIG. 12;

FIGS. 16-18 are side elevation views of the system of FIG. 12 inoperation;

FIG. 19 is simplified block diagram of a control algorithm or routinefor the system of FIG. 12;

FIG. 20 is a perspective view of another embodiment of the pest controldevice configured to be coupled to the pest trap device via integratedclips;

FIGS. 21-23 are side elevation views of the system of FIG. 20 inoperation;

FIG. 24 is a perspective view of another embodiment of the pest controldevice coupled to the pest trap device via integrated arms;

FIGS. 25-27 are side elevation views of the system of FIG. 24 inoperation;

FIG. 28 is a perspective view of another embodiment of the pest controldevice coupled to the pest trap device via an integrated channel;

FIGS. 29-31 are side elevation views of the system of FIG. 28 inoperation;

FIG. 32 is a perspective view of another embodiment of the pest controldevice of FIG. 3 mounted on a tomcat snap trap device; and

FIG. 33 is simplified block diagram of a control algorithm or routinefor the system of FIG. 12.

DETAILED DESCRIPTION OF THE DRAWINGS

While the concepts of the present disclosure are susceptible to variousmodifications and alternative forms, specific exemplary embodimentsthereof have been shown by way of example in the drawings and willherein be described in detail. It should be understood, however, thatthere is no intent to limit the concepts of the present disclosure tothe particular forms disclosed, but on the contrary, the intention is tocover all modifications, equivalents, and alternatives falling withinthe spirit and scope of the invention as defined by the appended claims.

Referring now to FIG. 1, a pest control system including a pest controlstation 10 is shown. In the illustrative embodiment, the pest controlstation 10 is a rodent control station 10 configured to monitor aparticular location. The station 10 includes a housing 12 and a pestcontrol device 14 positioned in the housing 12. As described in greaterdetail below, the pest control device 14 is configured to detect thepresence of rodents in the station 10 and report that presence to aremote system 16 wirelessly via an antenna 18. In other embodiments, thepest control device 14 may also include a pest trap device that detainsand/or exterminates the rodent. One exemplary pest trap device is shownin FIG. 12.

The station 10 also includes bait 20 in the form of a pest-consumablematerial. In some embodiments, the pest-consumable material may includea rodenticide. In other embodiments, the bait 20 may be a lure or otherpest-attracting material. In still other embodiments, the station 10 maynot include bait.

The control station may also be configured to monitor for the presenceof other pests such as, for example, termites, bed bugs, other insects,or other pests of concern. In those embodiments, the control station mayinclude a pest-specific sensor. The control station may also includebait in the form of a material that is consumable to the particularpest. Additionally, the bait may include an insecticide or otherpest-specific pesticide.

The housing 12 is illustratively formed from a hard, durable plastic,but, in other embodiments, it may be formed from any environmentallyresistant material. The housing 12 of the station 10 includes aplurality of outer walls 22 that define an inner chamber 24. The pestcontrol device 14 and the bait 20 are positioned in the chamber 24. Inthe illustrative embodiment, a pest may enter the station 10 through acircular opening 26 defined in each opposite wall 22.

The station 10 also includes a cover 28 that is hinged to the housing12. The cover 28 is illustratively formed from the same material as thehousing. The cover 28 is movable between the closed position shown inFIG. 1 and an open position (not shown) in which the chamber 24, andhence the control device 14 and bait 20, are accessible for maintenanceor other servicing. It should be appreciated that in other embodimentsthe cover may be removable from the housing. In still other embodiments,the cover may be omitted from the station 10.

As shown in FIG. 2, a passageway 30 of the inner chamber 24 of thehousing 12 connects the openings 26. The chamber 24 is divided by aninterior wall 32 into the passageway 30 and a bait chamber 34 that holdsthe bait 20. The interior wall 32 includes an opening 36 through which apest may enter the bait chamber 34 from the passageway 30, therebygaining access to the bait 20 positioned in the bait chamber 34. In theillustrative embodiment, the interior wall 32 is irregularly-shaped suchthat the inner chamber 24 is not divided equally between the passageway30 and the bait chamber 34. It should be appreciated that in otherembodiments the chamber 24 may include different arrangements ofpassageways and chambers. In still other embodiments, the chamber 24 mayconsist of only a single chamber.

As shown in FIG. 2, the pest control device 14 is embedded in a slot 40formed in the floor 42 of the housing 12. The slot 40 (and hence thecontrol device 14) is positioned in the passageway 30 in front of theopening 36. In that way, a pest entering and exiting the bait chamber 34passes over, or in proximity to, the pest control device 14 such thatthe control device 14 may detect the pest, as described in greaterdetail below. In some embodiments, bait may be placed in a cup or dishon the sensor of the control device 14 to lure the rodents onto thesensor. In the illustrative embodiment, the pest control device 14 isremovable from the slot 40 for replacement or other maintenance. Inother embodiments, the control device 14 may be integrally formed withthe housing 12 or otherwise not removable from the housing 12.

As described above, the pest control device 14 is configured to detectthe presence of rodents in the station 10 and report that presence to aremote system 16 wirelessly via an antenna 18. As shown in FIGS. 1-2,the antenna 18 is a whip antenna consisting of a single straightflexible metal wire. The antenna 18 is connected at its base to the pestcontrol device 14 via a connector 44. In that way, the pest controldevice 14 may be disconnected from the antenna 18. In other embodiments,the pest control device 14 and the antenna 18 may be formed as a singleunit. It should also be appreciated that in other embodiments theantenna 18 may be a low-profile helical antenna, hardware circuit in thepest control device 14, or other type of antenna capable of transmittingand receiving signals between the pest control device 14 and the system16.

As shown in FIG. 3, the antenna connector 44 extends outwardly from therear wall 50 of an outer casing 52 of the pest control device 14. Theouter casing 52 houses the electrical components 54, which include apair of light emitting diodes (LEDs) 56, 58. In the illustrativeembodiment, the LEDs 56, 58 are positioned in openings defined in thetop surface 60 of the casing 52 and are configured to emit differentcolors (red and green, respectively) to indicate status of the pestcontrol device 14. In other embodiments, LEDs emitting other colors orthe same color may be used. In still other embodiments, other indicatorsmay be used to indicate visually or audibly the status of the pestcontrol device 14.

The casing 52 is illustratively formed from a plastic material thatprotects the electrical components 54 from environmental factors,including water ingress, dust, dirt, leaves, humidity, and waste. Itshould be appreciated that in other embodiments other materials may beused in the casing 52. The casing 52 measures approximately 50 mm by 75mm by 15 mm. It should be appreciated that in other embodiments thecasing 52 (and hence the control device 14) may be larger or smallerdepending on, for example, the nature of the pest and the monitoringenvironment.

Referring now to FIG. 4, the electrical components 54 of the pestcontrol device 14 are shown in a simplified block diagram. In theillustrative embodiment, the electrical components 54 include circuitsand circuitry as well as electronic devices such as an electroniccontrol unit (ECU) or “electronic controller” 62, which is configured tocontrol the operation of the pest control device 14. The ECU 62 isillustratively embodied as a lower-power microcontroller device such asa MSP430 Series microcontroller, which is commercially available fromTexas Instruments of Dallas, Tex. In other embodiments, othercommercially-available microcontrollers, discrete processing circuits(e.g., a collection of logic devices), general purpose integratedcircuit(s), and/or application specific integrated circuit(s) (i.e.,ASICs) may be used to control the operation of the pest control device14. In the illustrative embodiment, the other electrical components 54,including the LEDs 56, 58, are electrically connected with the ECU 62via a number of communication links 64 such as printed circuit boardtraces, wires, cables, and the like.

The electrical components 54 include a transceiver array 66 that isconnected to the antenna 18 via the connector 44. The transceiver array66 is configured to transmit and/or receive data for the ECU 62 using aradio frequency over a local area network (LAN). In the illustrativeembodiment, the transceiver array 66 is capable of communication in theunlicensed 915 MHz Industrial, Scientific, and Medical (ISM) frequencyband. As such, the transceiver array 66 may include any number ofcircuits and electronic devices (e.g., an RF transceiver and duplexer).In the illustrative embodiment, the RF transceiver of the array 66 is alow power transceiver such as, for example, a Simplelink CC1200 RFTransceiver, which is commercially available from Texas Instruments ofDallas, Tex. It should be appreciated that in other embodiments thetransceiver array may be configured to transmit and receive using acellular network. In other embodiments, the pest sensor may include aseparate transmitter and receiver for transmitting and receiving datafrom the remote system. In still other embodiments, the pest sensor maybe configured to be hardwired to a communication network via a cable.

As shown in FIG. 4, the pest control device 14 includes a capacitivesensor array 70 that is configured to generate electrical output signalswhen a rodent passes over the pest control device 14. The sensor array70 illustratively includes five sensor pads 72, which are arranged in a“X” pattern similar to the “5” face of a gaming dice. Each pad 72 issubstantially circular and is connected to a specific pin of the ECU 62via a relaxation oscillator circuit (not shown). Each pad 72 is alsoconfigured to provide higher sensitivity on the side 74, which facestoward the top surface 60 of the casing 52 (i.e., the surface contactedby the rodent), and less sensitivity on the side 76 (see FIG. 5) facingaway from that surface. In the illustrative embodiment, the differencein sensitivity is accomplished through selection of the pad diameter,spacing between the pad and adjacent ground area, and the addition of agrounding pattern on the side 76 of each pad 72. As shown in FIG. 5, thegrounding pattern takes the form of a cross-hatch pattern 78. It shouldbe appreciated that other sensor array may be used in other embodiments.

Each pad 72 of the array 70 is formed from copper, but, in otherembodiments, Indium tin oxide (ITO) and printed ink may be used. In theillustrative embodiment, the array 70 is configured to generate anelectrical output signal when an object (such as a rodent) passes overone of the pads 72, thereby changing the dielectric field between thepad 72 and its ground layer. A signal corresponding to the change in thedielectric field is communicated to the ECU 62, which uses thatinformation as described in greater detail below.

As shown in FIG. 4, the pest control device 14 also includes a number ofenvironmental sensors to provide information about the monitoringlocation and the pest control device 14. The environmental sensorsinclude a temperature sensor 80 configured to measure the temperature ofthe environment surrounding the station 10. In the illustrativeembodiment, the temperature sensor is a digital sensor such as, forexample, the STLM75, which is commercially available fromSTMicroelectronics. The temperature sensor 80 is configured to take atemperature measurement and transmit a signal indicative of thatmeasurement to the ECU 62.

The electrical components 54 of the control device 14 also include aposition/orientation sensor 84 configured to detect movement of thestation 10. In the illustrative embodiment, the orientation sensor 84 isa 3-axis digital accelerometer such as, for example, the MMA8652, whichis commercially available from Freescale. The sensor 84 detects movementof the control device 14 and transmits a signal indicative of thatmovement to the ECU 62. When the sensor 84 is positioned in the station10 and the station 10 is moved, the sensor 84 detects that movement andtransmits its signal to the ECU 62. The sensor 84 may also be configuredto detect entry of the rodent into the station 10 and/or the closing ofa rodent trap.

In other embodiments, the position sensor 84 may be a Hall-Effect sensorthat detects the proximity of the sensor 84 (and hence the station 10)to a magnetic anchor secured to the ground or otherwise separated fromthe station 10. In such embodiments, movement of the station 10 relativeto the magnetic anchor causes the sensor 84 to generate a signalindicative of that movement and transmit that signal to the ECU 62. Whena magnetic anchor is incorporated into the housing 12, the Hall-Effectsensor may also be used to determine if the position sensor 84 isproperly positioned in the station 10. It should be appreciated that inother embodiments the position sensor 84 may be omitted.

It should be appreciated that in other embodiments the pest controldevice 14 may include other environmental sensors 82. Such sensors 82may measure humidity, air quality, dampness, or other factors that mayaffect the operation of the control device 14, the status of the bait20, and/or the state of the station 10.

As shown in FIG. 4, the control device 14 is powered by a local battery86. In the illustrative embodiment, the battery 86 is a lithium thionylchloride battery that is not replaceable. It should be appreciated thatin other embodiments other battery types may be used. In still otherembodiments, the control device 14 may utilize an external power source.

The control device 14 also includes a proximity sensor 88 configured todetect a magnetic source such as, for example, a magnetic wand that maybe present during maintenance. In the illustrative embodiment, theproximity sensor 88 is a Hall-Effect sensor that generates a signal toindicate the presence of the magnetic source and transmit that signal tothe ECU 62. It should be appreciated that other embodiments mayimplement a different detection mechanism that includes additional orfewer components to detect the presence of rodents in the station 10.

As described above, the electrical components 54 are connected to, andcommunicate with, the ECU 62, which is, in essence, the master computerresponsible for interpreting electrical signals sent by sensorsassociated with the control device 14 and for activating or energizingelectronically-controlled components associated with control device 14.For example, the ECU 62 is configured to control operation of the LEDs56, 58 and the transceiver array 66. The ECU 62 also monitors varioussignals from the capacitive sensor array 70 and the sensors 80, 84, 88and determines when various operations of the control device 14 shouldbe performed. As will be described in more detail below with referenceto FIGS. 6-7, the ECU 62 is operable to control the components of thecontrol device 14 such that the pest activity and other informationabout the station 10 are communicated to the remote system 16.

To do so, the ECU 62 includes a number of electronic components commonlyassociated with electronic units utilized in the control ofelectromechanical systems. For example, the ECU 62 includes, amongstother components customarily included in such devices, a processor suchas a microprocessor 90 and a memory device 92 such as a programmableread-only memory device (“PROM”) including erasable PROM's (EPROM's orEEPROM's). The memory device 92 is provided to store, amongst otherthings, instructions in the form of, for example, a software routine (orroutines) which, when executed by the microprocessor 90, allows the ECU62 to control operation of the control device 14.

The ECU 62 also includes an analog interface circuit 94. The analoginterface circuit 94 converts the output signals from various sensors(e.g., the proximity sensor 88 and capacitive sensor array 70) intosignals which are suitable for presentation to an input of themicroprocessor 90. In particular, the analog interface circuit 94, byuse of an analog-to-digital (A/D) converter (not shown) or the like,converts the analog signals generated by the sensors into digitalsignals for use by the microprocessor 90. It should be appreciated thatthe A/D converter may be embodied as a discrete device or number ofdevices, or may be integrated into the microprocessor 90. For thosesensors of the control device 14 that generate a digital output signal,the analog interface circuit 94 may be bypassed.

Similarly, the analog interface circuit 94 converts signals from themicroprocessor 90 into output signals which are suitable forpresentation to the electrically-controlled components of the controldevice 14 (e.g., the LEDs 56, 58). In particular, the analog interfacecircuit 94, by use of a digital-to-analog (D/A) converter (not shown) orthe like, converts the digital signals generated by the microprocessor90 into analog signals. It should be appreciated that, similar to theA/D converter described above, the D/A converter may be embodied as adiscrete device or number of devices, or may be integrated into themicroprocessor 90. For those electronically-controlled components thatoperate on a digital input signal, the analog interface circuit 94 maybe bypassed.

Thus, the ECU 62 may control the operation of the control device 14. Inparticular, the ECU 62 executes a routine including, amongst otherthings, a control scheme in which the ECU 62 monitors outputs of thesensors associated with the control device 14 to control the inputs tothe electronically-controlled components associated therewith. To do so,the ECU 62 communicates with the sensors associated with the controldevice 14 to determine, amongst numerous other things, the state of thepads 72, the temperature of the environment, movement of the device 14,and so forth. Armed with this data, the ECU 62 performs numerouscalculations, either continuously or intermittently, including lookingup values in preprogrammed tables, in order to execute algorithms toperform such functions as transmitting or receiving data from the remotesystem 16, energizing the LEDs 56, 58, et cetera. It should beappreciated that in other embodiments, the ECU may be implemented asfield programmable gate array (FPGA) or other programmable logic device,a digital signal processor (DSP), an application specific integratedcircuit (ASIC), or any other configuration that is designed to performthe functions described herein.

To conserve battery power, the ECU 62 is configured to enter a reducedpower mode between operations. In the illustrative embodiment, the ECU62 is configured to exit the reduced power mode every 100 millisecondsand execute a control routine similar to the control routine 100illustrated in FIG. 6. It should be appreciated that while the operationblocks of the routine 100 are shown in sequence, the ECU 62 may performone or more of the operations depicted therein simultaneously or in anorder different from that shown in FIG. 6. It should also be appreciatedthat in other embodiments one or more of the operation blocks may beomitted.

The routine 100 begins with block 102 in which the ECU 62 monitors thecapacitive sensor array 70 and determines if there is any activity. Todo so, the ECU 62 executes the sub-routine 200 illustrated in FIG. 7.The sub-routine 200 begins with block 202 in which the ECU 62 measuresthe capacitance of each of the pads 72 of the capacitive sensor array70. In block 202, the ECU 62 separately measures the frequency of eachof the five relaxation oscillator circuits connected to each pad 72. Thefrequency of each oscillator circuit is inversely related to thecapacitance between its corresponding pad 72 and ground area. Asdescribed above, when a rodent is proximate to, or passes over, a pad72, the dielectric constant of the capacitor formed by that pad 72 andthe ground area is affected, thereby changing the capacitance of thecapacitor and hence the frequency output of the oscillator circuit.After the ECU 62 has measured the capacitance of each of the pads 72,the sub-routine 200 advances to block 204.

In block 204, the ECU 62 calculates a new baseline for each pad 72 basedon the measured capacitance for that pad. In the illustrativeembodiment, the ECU 62 is configured to execute Equations (1) and (2)below, which use a programmable time constant (Kf) to change the rate atwhich the baselines are adapted to the environment.

$\begin{matrix}{{A({new})} = {{A({old})} - {{A({old})}*\left( \frac{Kf}{2^{16}} \right)} + {{Measured}\mspace{14mu}{Capacitance}}}} & (1) \\{{Baseline} = {{A({new})}*\left( \frac{Kf}{2^{16}} \right)}} & (2)\end{matrix}$

Each baseline value and each value of variable A(new) is stored inmemory for future use by the ECU 62. As described in greater detailbelow, the parameter Kf may be changed or updated by the remote system16 based on environmental factors and past activity recorded by the pestcontrol device 14.

In block 206, the ECU 62 compares each capacitance measured in block 202against the corresponding new/adapted baseline value calculated in block204 and calculates the differences between those values. The comparisonof each capacitance measured in block 202 against an adapted baselinevalue enables the sensor to adapt to gradual changes in its environmentwhile retaining the necessary sensitivity and precision to detect pestactivity. In that way, the ECU 62 obtains five difference values, onefor each pad 72. The sub-routine 200 then advances to block 208.

In block 208, the ECU 62 determines whether any of the calculateddifferences exceed a stored “Pest Value” threshold. The Pest Valuethreshold is programmable and is determined based on, among otherthings, the nature of the rodent and environment surrounding thestation. The Pest Value threshold may be changed or updated by theremote system 16 based on environmental factors and past activityrecorded by the pest control device 14. Each pad 72 may have the same ora different Pest Value threshold. When no calculated difference exceedsits corresponding Pest Value threshold, the sub-routine 200 ends. Whenat least one calculated difference exceeds its corresponding Pest Valuethreshold, the sub-routine 200 advances to block 210.

In block 210, the ECU 62 determines whether any of the calculateddifferences exceed a stored “Human Value” threshold. The Human Valuethreshold is programmable and is used to determine whether a serviceperson or other individual is deliberately interacting with the pestcontrol device 14. The Human Value threshold may be changed or updatedby the remote system 16. Each pad 72 may have the same or a differentHuman Value threshold. When no calculated difference exceeds itscorresponding Human Value threshold, the sub-routine 200 advances toblock 212. When at least one calculated difference exceeds itscorresponding Human Value threshold, the sub-routine 200 advances toblock 214.

The ECU 62 updates software counters for the pads 72 in block 212, andthe sub-routine 200 advances to block 216. In block 216, the softwarecounter associated with each pad 72 is compared against a Counter Limitparameter stored in memory. The Counter Limit parameter may be changedor updated by the remote system 16. Each pad 72 may have the same or adifferent Counter Limit parameter. If any of the counters exceed theircorresponding Counter Limit, the ECU 62 records a pest event in memoryin block 218 and activates one or both of the LEDs 56, 58 in block 220to visually indicate detection of a pest, as described in greater detailbelow. In that way, a pest event may be recorded even if the rodentcontacts a single pad 72. If all of the counters are less than theircorresponding Counter Limit, the sub-routine 200 ends.

As described above, the sub-routine 200 advances to block 214 when atleast one difference between a pad capacitance and its baseline exceedsa corresponding Human Value threshold. In block 214, the ECU 62 executesan algorithm to determine the sequence of pad hits or contacts. Thatsequence is compared in block 222 to a predetermined sequence ofindividual pad hits that is unlikely to occur when a rodent is inproximity to the control device 14. For example, in the illustrativeembodiment, the sequence of hits may correspond to a human swiping afinger across the capacitive sensor array 70 to draw the letter “X”(indicating hits to all five pads). In other embodiments, the sequencemay correspond to other geometric shapes such as, for example, a square(indicating hits to the four outer pads). When the contact sequencematches the predetermined sequence, the sub-routine 200 advances toblock 224. When the contact sequence is different from the predeterminedsequence, the sub-routine 200 ends. In other embodiments, thesub-routine 200 may advance to block 212 to increment the softwarecounter associated with a possible pest event.

In block 224, the ECU 62 records a service event in memory, and thesubroutine 200 advances to block 220 in which the ECU 62 energizes oneor both of the LEDs 56, 58 to provide a visual indication of thedetection of the service event. For example, only the green LED 58 isenergized to indicate the successful detection of a service event orother human interaction with the control device 14. In response todetecting a pest event in block 218, both LEDs 56, 58 are energized toflash simultaneously.

At the end of the sub-routine 200, the routine 100 may advance to block104, as shown in FIG. 6. In block 104, the ECU 62 monitors the variousenvironmental sensors, including the temperature sensor 80 and theposition sensor 82. To do so, the ECU 62 accesses the data from thetemperature sensor 80 and stores a temperature value in memory. The ECU62 also accesses the data received from the accelerometer 84. If thedata received from the accelerometer 84 indicates movement, the ECU 62records the event in memory. The routine 100 may then advance to block106.

In block 106, the ECU 62 monitors the magnetic proximity sensor 88. Ifthe sensor 88 determines the presence of a magnetic source such as, forexample, a magnetic wand, the ECU 62 records a service event in memory.The ECU 62 also activates one or both of the LEDs 56, 58 in apredetermined sequence to indicate that the control device 14 detectedthe event. In some embodiments, the ECU 62 may also be configured toclear all of the counters when the magnetic source is detected. Theroutine 100 may then advance to block 108.

In block 108, the ECU 62 samples the voltage of the battery 86 using theanalog interface circuit 94. The measured voltage is then compared tothresholds stored in memory using an algorithm to determine theapproximate state of the charge of the battery 86. The state of thecharge may then be stored in memory. The routine 100 may then advance toblock 110.

In block 110, the pest control device 14 communicates with the remotesystem 16. The remote system 16 includes communications middleware,database, and application software and may be located on site with thepest control device 14 or off site. A range extender may be used toextend a range of a wireless network to transmit data received from thepest control device. The remote system 16 may also include a basestation, which may include a transceiver that receives data directlyfrom the pest control device or indirectly via the range extender andtransmits data to a network-based utility via a cellular wirelessnetwork. The base station may also receive data from the network-basedutility and transmit that data to the pest control device directly orindirectly via the range extender. The network-based utility may befurther integrated with different interfaces, such as a managementportal, mobile service interfaces, or billing interface. Through theseinterfaces, the data may be further processed, analyzed, stored, orfurther transmitted to web or mobile services. One example of anetwork-based utility is MeshVista®, which is commercially available byMesh Systems™.

To transmit its data to the remote system 16, the ECU 62 energizes thetransceiver array 66 to establish contact with the remote system 16 viathe local area network (LAN). The transmitted data may include, amongother things, the recorded pest events, service events, temperaturemeasurements, records of movement, the baseline values for the pads 72,the state of the charge of the battery 86, and so forth. The pestcontrol device 14 may also transmit an indication of the health of theLAN communications infrastructure. The pest control device 14 furtherenergizes and de-energizes the LEDs 56, 58 depending on its connectionto the network. For example, the LED 58 may be flashed for a ten secondinterval to indicate a successful connection, while the LED 56 may beflashed for a ten second interval to indicate no connection with thenetwork.

The remote system 16 may then interpret the data and transmit updatedparameters back to the control device 14. The remote system 16 mayupdate, for example, the Pest Value threshold if a number of falsepositives have been logged at the control device 14. The updatedparameters may include the programmable constant Kf, the Human Valuethreshold, the Pest Value threshold, and the software counter limit foreach pad. Additionally, the remote system 16 may change thepredetermined sequence of pad contacts used to indicate a service event.The ECU 62 updates the parameters stored in memory in block 112 beforereturning to the reduced power mode.

As described above, the routine 100 includes a block 102 in which theECU 62 monitors the capacitive sensor array 70 and determines if thereis any activity. It should be appreciated that the routine 100 mayinclude other sub-routines that may be executed by the ECU 62 todetermine if there is activity at a particular sensor. One suchsub-routine (hereinafter sub-routine 280) is shown in FIG. 8. Thesub-routine 280 begins with block 282 in which the ECU 62 determines thecondition of each pad 72 of the capacitive sensor array 70. In theillustrative embodiment, the new pad conditions may be “Active,”indicating the presence of pest activity, or “Inactive,” indicating nopest activity. To determine the new pad condition for each pad 72, theECU 62 may execute sub-routine 300 illustrated in FIG. 9, which isdescribed in greater detail below.

After the ECU 62 determines the new pad condition for each pad 72, thesub-routine 280 advances to block 284 in which the new pad condition foreach pad 72 is compared to the previous pad condition for that pad. Todo so, the ECU 62 may retrieve the previous conditions for the array 70that are stored in memory 92 and compare the previous conditions to thenew conditions. If the new condition of any pad 72 is not equal to theprevious condition recorded for that pad, the sub-routine 280 advancesto block 286. For example, if the new condition for one pad 72 is“Inactive” and the previous condition was recorded as “Active” for thatpad, the sub-routine 280 would advance to block 286, even if the newconditions for the other pads were the same as their correspondingprevious conditions. In that way, the change of condition of just onepad will advance the sub-routine 280 to block 286. If the new conditionsof all of the pads 72 are the same as the previous conditions stored inmemory, the sub-routine 280 ends, and the routine 100 may advance toblock 104, which is described above.

In block 286 of the sub-routine 280, the ECU 62 sets the current padcondition for each pad 72 equal to the new condition determined for thatpad in block 282, and the sub-routine 280 advances to block 288. Inblock 288, the ECU 62 records a pest event if one of the current padconditions set in block 286 is labeled “Active.” If all of the currentpad conditions are labeled “Inactive,” the ECU 62 does not record a pestevent.

At the completion of block 288, the sub-routine 280 advances to block290 in which the ECU 62 stores the current pad conditions as previouspad conditions in the memory 92. In that way, the conditions areavailable for use when the ECU 62 next executes the sub-routine 280. Thesub-routine 280 then ends, and the routine 100 may advance to block 104.

Referring now to FIG. 9, an exemplary sub-routine 300 for use indetermining new pad conditions in block 282 of the sub-routine 280 isshown. The sub-routine 300 begins with block 302 in which the ECU 62selects one of the pads 72 of the capacitive sensor array 70 to query.With that pad 72 selected, the sub-routine 300 proceeds to block 304. Inblock 304, the ECU 62 measures the frequency of the relaxationoscillator circuit connected to the selected pad 72. As described above,the frequency of each oscillator circuit is inversely related to thecapacitance between the selected pad 72 and ground area. After the ECU62 has measured the capacitance of the selected pad 72, the sub-routine300 advances to block 306.

In block 306, the ECU 62 calculates a new baseline for the selected pad72 based on the capacitance measured in block 304. To do so, the ECU 62may use Equations (1) and (2) presented above to obtain a baseline valuethat is adapted to the environment. After the ECU 62 calculates the newbaseline, the sub-routine 300 advances to block 308 in which the ECU 62compares the capacitance value measured in block 304 against thenew/adapted baseline value calculated in block 306. The ECU 62calculates the difference between those values, and the sub-routine 300then advances to block 310.

In block 310, the ECU 62 determines whether the calculated differenceexceeds a stored “Pest Value” threshold. Like the sub-routine 200, thePest Value threshold of the sub-routine 300 is programmable and isdetermined based on, among other things, the nature of the rodent andenvironment surrounding the station. The Pest Value threshold may bechanged or updated by the remote system 16 based on environmentalfactors and past activity recorded by the pest control device 14. Eachpad 72 may have the same or a different Pest Value threshold. When thecalculated difference for the selected pad 72 exceeds the Pest Valuethreshold for that pad, the sub-routine 300 advances to block 312. Whenthe calculated difference is less than the Pest Value threshold, thesub-routine 300 advances to block 314.

In block 312, the ECU 62 sets a variable—identified in FIG. 9 as “rawcondition”—to “Active” when the calculated difference for the selectedpad 72 exceeds the Pest Value threshold for that pad. If executing thealternative block 314, the ECU 62 sets the raw condition for theselected pad 72 to “Inactive” because the calculated difference is lessthan the Pest Value threshold. After completing either block 312 orblock 314, the sub-routine 300 advances to block 316.

In block 316, the ECU 62 compares the raw condition to the previous padcondition for the selected pad 72. As described above, the previous padconditions for the capacitive sensor array 70 are stored in the memory92. The ECU 62 retrieves the previous pad condition for the selected pad72 from memory and compares it to the raw condition. If the raw padcondition is equal to or the same as the previous pad condition, thesub-routine 300 advances to block 318 in which the ECU 62 resets thesoftware counter for the selected pad 72 to zero, and the sub-routine300 advances to block 320. If the raw pad condition for the selected pad72 is not equal to or the same as the previous pad condition, thesub-routine 300 advances directly from block 316 to block 320.

In block 320, the software counter associated with the selected pad 72is compared against a Counter Limit parameter stored in memory. TheCounter Limit parameter may be changed or updated by the remote system16, and each pad 72 may have the same or a different Counter Limitparameter. If the counter for the selected pad 72 exceeds itscorresponding Counter Limit, the sub-routine 300 advances to block 322.If the software counter for the selected pad 72 is less than itscorresponding Counter Limit, the sub-routine 300 advances to block 324.

In block 322, the ECU 62 sets a new condition for the selected pad 72equal to the raw condition of that pad. For example, if the rawcondition is equal to “Active,” the ECU 62 sets the new pad condition to“Active.” The sub-routine 300 then advances from block 322 to block 328,which is described in greater detail below.

Returning to block 320, if the software counter for the selected pad 72is less than its corresponding Counter Limit, the sub-routine 300advances to block 324 in which the software counter for the selected padis incremented. The sub-routine 300 then advances to block 326 in whichthe ECU 62 sets the new condition for the selected pad equal to theprevious condition stored in memory. The sub-routine 300 advances fromblock 326 to block 328.

In block 328, the ECU 62 analyzes whether it has determined new padconditions for all of the pads 72. If the ECU 62 has not determined newpad conditions for all of the pads 72 in the array 70, the sub-routine300 advances to block 330 in which the ECU 62 selects another pad 72,and the sub-routine 300 returns to block 304. The ECU 62 repeats blocks304 through block 328 until new pad conditions have been determined forall of the pads 72, at which point the sub-routine 300 ends. Thesub-routine 280 of FIG. 8 may then advance to block 284 of thesub-routine 280, which is described above in regard to FIG. 8.

Another sub-routine (hereinafter sub-routine 370) for use in determiningif there is activity at a particular sensor is shown in FIG. 10. Thesub-routine 370 begins with block 372 in which the ECU 62 determines thenew condition of each pad 72 of the capacitive sensor array 70. In theillustrative embodiment, the new pad conditions include both pad pestconditions, which relate to possible pest activity, and pad humanconditions, which relate to possible human activity. To determine thenew pad conditions for the pads 72, the ECU 62 may execute sub-routine400 illustrated in FIGS. 11a and 11 b.

The sub-routine 400 shown in FIGS. 11a and 11b includes a number ofblocks that are the same or similar to the blocks of the sub-routine300. For such blocks, the references numbers from the sub-routine 300described above will be used to identify those blocks in the sub-routine400. For example, the sub-routine 400, like the sub-routine 300, beginswith a block 302 in which the ECU 62 selects one of the pads 72 of thecapacitive sensor array 70 to query. The sub-routine 400 then proceedsthrough block 304 to block 310 as shown in FIG. 11a . As describedabove, the ECU 62 determines in block 310 whether any of the calculateddifference for the selected pad 72 exceeds a stored “Pest Value”threshold. When the calculated difference for the selected pad 72exceeds the Pest Value threshold for that pad, the sub-routine 400advances to block 412. When the calculated difference is less than thePest Value threshold, the sub-routine 400 advances to block 414.

In block 412, the ECU 62 sets a variable—identified in FIG. 11a as “rawpest condition”—to “Active” when the calculated difference for theselected pad 72 exceeds the Pest Value threshold for that pad. Ifexecuting the alternative block 414, the ECU 62 sets the raw pestcondition for the selected pad 72 to “Inactive” because the calculateddifference is less than the Pest Value threshold. After completingeither block 412 or block 414, the sub-routine 400 advances to block416.

In block 416, the ECU 62 compares the raw pest condition to the previouspest condition for the selected pad 72. The previous pest conditions forthe capacitive sensor array 70 are stored in the memory 92. The ECU 62retrieves the previous pest condition for the selected pad 72 frommemory and compares it to the raw pest condition. If the raw pestcondition is equal to or the same as the previous pest condition, thesub-routine 400 advances to block 418 in which the ECU 62 resets thesoftware pest counter for the selected pad 72 to zero, and thesub-routine 400 advances to block 420. If the raw pest condition for theselected pad 72 is not equal to or the same as the previous pestcondition, the sub-routine 400 advances directly from block 416 to block420.

In block 420, the software pest counter associated with the selected pad72 is compared against a Pest Counter Limit parameter stored in memory.The Pest Counter Limit parameter may be changed or updated by the remotesystem 16, and each pad 72 may have the same or a different Pest CounterLimit parameter. If the pest counter for the selected pad 72 exceeds itscorresponding Pest Counter Limit, the sub-routine 400 advances to block422. If the software pest counter for the selected pad 72 is less thanits corresponding Counter Limit, the sub-routine 400 advances to block424.

In block 422, the ECU 62 sets a new pest condition for the selected pad72 equal to the raw pest condition of that pad. For example, if the rawpest condition is equal to “Active,” the ECU 62 sets the new pestcondition to “Active.” The sub-routine 400 then advances from block 422to block 428 in FIG. 11b , which is described in greater detail below.

Returning to block 420, if the software counter for the selected pad 72is less than its corresponding Pest Counter Limit, the sub-routine 400advances to block 424 in which the software counter for the selected padis incremented. The sub-routine 400 then advances to block 426 in whichthe ECU 62 sets the new pest condition for the selected pad equal to theprevious pest condition stored in memory. The sub-routine 400 advancesfrom block 426 to block 428 in FIG. 11 b.

In block 428, the ECU 62 determines if the difference calculated inblock 308 between the measured capacitance value and the baseline valuefor the selected pad 72 exceeds a corresponding Human Value thresholdfor that pad. The Human Value threshold is programmable and is used todetermine whether a service person or other individual is deliberatelyinteracting with the pest control device 14. The Human Value thresholdmay be changed or updated by the remote system 16. Each pad 72 may havethe same or a different Human Value threshold. When the calculateddifference exceeds the Human Value threshold for the selected pad 72,the sub-routine 400 advances to block 430. When the calculateddifference is less than the Human Value threshold, the sub-routine 400advances to block 432.

In block 430, the ECU 62 sets a variable—identified in FIG. 11b as “rawhuman condition”—to “Active” when the calculated difference for theselected pad 72 exceeds the Human Value threshold for that pad. Ifexecuting the alternative block 432, the ECU 62 sets the raw humancondition for the selected pad 72 to “Inactive” because the calculateddifference is less than the Human Value threshold. After completingeither block 430 or block 432, the sub-routine 400 advances to block434.

In block 434, the ECU 62 compares the raw human condition to theprevious human condition for the selected pad 72. The previous humanconditions for the capacitive sensor array 70 are stored in the memory92. The ECU 62 retrieves the previous human condition for the selectedpad 72 from memory and compares it to the raw human condition. If theraw human condition is equal to or the same as the previous humancondition, the sub-routine 400 advances to block 436 in which the ECU 62resets the software human counter for the selected pad 72 to zero, andthe sub-routine 400 advances to block 438. If the raw human conditionfor the selected pad 72 is not equal to or the same as the previoushuman condition, the sub-routine 400 advances directly from block 434 toblock 438.

In block 438, the software human counter associated with the selectedpad 72 is compared against a Human Counter Limit parameter stored inmemory. The Human Counter Limit parameter may be changed or updated bythe remote system 16, and each pad 72 may have the same or a differentHuman Counter Limit parameter. If the human counter for the selected pad72 exceeds its corresponding Human Counter Limit, the sub-routine 400advances to block 440. If the software human counter for the selectedpad 72 is less than its corresponding Counter Limit, the sub-routine 400advances to block 442.

In block 440, the ECU 62 sets a new human condition for the selected pad72 equal to the raw human condition of that pad. For example, if the rawhuman condition is equal to “Active,” the ECU 62 sets the new humancondition to “Active.” The sub-routine 400 then advances from block 440to block 328, which is described in greater detail below.

Returning to block 438, if the software counter for the selected pad 72is less than its corresponding Human Counter Limit, the sub-routine 400advances to block 442 in which the software human counter for theselected pad is incremented. The sub-routine 400 then advances to block444 in which the ECU 62 sets the new human condition for the selectedpad equal to the previous human condition stored in memory. Thesub-routine 400 advances from block 444 to block 328.

In block 328, the ECU 62 analyzes whether it has determined new padconditions for all of the pads 72. If the ECU 62 has not determined newpad conditions for all of the pads 72 in the array 70, the sub-routine400 advances to block 330 in which the ECU 62 selects another pad 72,and the sub-routine 400 returns to block 304 in FIG. 11a . The ECU 62repeats the process of obtaining new pad conditions until new padconditions have been determined for all of the pads 72, at which pointthe sub-routine 400 ends. The sub-routine 370 of FIG. 10 may thenadvance to block 374 of the sub-routine 370.

Returning to FIG. 10, the sub-routine 370 advances from block 372 toblock 374 in which the new pest condition for each pad 72 is compared tothe previous pest condition for that pad. To do so, the ECU 62 mayretrieve the previous pest conditions for the array 70 that are storedin memory 92 and compare the previous pest conditions to the new pestconditions. If the new pest condition of any pad 72 is not equal to orthe same as the previous pest condition recorded for that pad, thesub-routine 370 advances to block 376. In that way, the change of pestcondition of just one pad will advance the sub-routine 370 to block 376.If the new pest conditions of all of the pads 72 are the same as theprevious conditions recorded in memory, the sub-routine 370 advances toblock 378.

In block 376, of the sub-routine 370, the ECU 62 sets the current pestconditions equal to the new pest conditions determined in block 372, andthe sub-routine 370 advances to block 380. In block 380, the ECU 62records a pending pest event if one of the current pad pest conditionsset in block 376 is labeled “Active.” If all of the current padconditions are labeled “Inactive,” the ECU 62 does not record a pendingpest event. The sub-routine 370 then advances to block 378.

In block 378, the ECU 62 compares the new human condition for each pad72 to the previous human condition for that pad recorded for that pad.To do so, the ECU 62 may retrieve the previous human conditions for thearray 70 that are stored in memory 92. If the new human condition of anypad 72 is not equal to or the same as the previous human conditionrecorded for that pad, the sub-routine 370 advances to block 382. Inthat way, the change of human condition of just one pad will advance thesub-routine 370 to block 382. If the new human conditions of all of thepads 72 are the same as the previous human conditions recorded inmemory, the sub-routine 370 advances to block 384.

In block 382, the ECU 62 reviews all of the new human conditions for thesensor pads 72 to determine if any of the new human conditions satisfy arequired sequence of pad hits or contacts. As described above, the ECU62 may execute an algorithm to determine the sequence of pad hits orcontacts. For example, in the illustrative embodiment, the sequence ofhits may correspond to a human swiping a finger across the capacitivesensor array 70 to draw the letter “X” (indicating hits to all fivepads). If any of the new human conditions correspond to an expected hitor contact to satisfy the sequence, the sub-routine 370 advances toblock 386. If no new human conditions correspond to an expected contactto satisfy the sequence, the sub-routine 370 advances to block 388 inwhich the ECU 62 resets the sequence.

In block 386, the ECU 62 determines whether a combination of new humanconditions and previous human conditions for the sensor array 70completes the required sequence (i.e., indicates the presence of ahuman). If the sequence is completed, the sub-routine 370 advances toblocks 390, 392 in which the ECU 62 records a service event and discardsthe pending pest event created in block 378 so that the event isrecorded only as a service event and not as a pest event. At thecompletion of block 392, the sub-routine 370 ends. Similarly, if the ECU62 determines in block 386 that the sequence is not completed, thesub-routine 370 ends.

Returning to block 378, if ECU 62 determines the new human conditions ofall of the pads 72 are the same as the previous human conditionsrecorded in memory, the sub-routine 370 advances to block 384. In block384, the ECU 62 confirms whether it is looking for the sequence of padhits or contacts. If it is, the sub-routine 370 ends; if it is not, thesub-routine 370 advances to block 394. In block 394, ECU 62 records apest event based on the pending pest event recorded in block 380. Thesub-routine 370 then ends. At the completion of the sub-routine 370, theroutine 100 may advance to block 104, as described above.

Referring now to FIGS. 12-18, a pest control system 510 is shown withanother embodiment of a pest control device (hereinafter referred to aspest control device 514) and a pest trap device 516. The embodiment ofFIGS. 12-18 includes many of the same features described above in regardto FIGS. 1-11. The same reference numbers are used in FIGS. 12-18 toidentify features that are the same or similar to those described abovein regard to FIGS. 1-11. As shown in FIG. 12, the pest control device514 may be coupled to a snap-type rodent trap 516 that detains and/orexterminates the rodent. In operation, the pest control device 514includes a position or orientation sensor 84 that is operable to detectmovement of the pest control device 514, as described in greater detailbelow, and report that movement of the pest control device 514 to aremote system 16 wirelessly via an antenna 18 to provide an indicationof whether the trap 516 has been activated.

Similar to the position/orientation sensor 84 described above in regardto FIGS. 1-11, the orientation sensor 84 is a 3-axis digitalaccelerometer such as, for example, the MMA8652, which is commerciallyavailable from Freescale. In some embodiments, the position sensor maybe operable to detect movement of a trap. In such embodiments, theposition sensor may be embedded in the trap to monitor changes incondition of the trap. The position sensor may also be configured totransmit its accelerometer readings to the pest control device ordirectly to the system 16, via wired or wireless connection.

As shown in FIGS. 12-13, the pest control device 514 includes an outercasing 520 and a hinged support leg 522 attached to the casing 520. Theouter casing 520, like the casing 52 described above in regard to FIGS.1-11, houses and protects the electrical components 54 fromenvironmental factors, including water ingress, dust, dirt, leaves,humidity, and waste. In the illustrative embodiment, the electricalcomponents 54 of the device 514 are the same or similar to theelectrical components of the device 14, including the position sensor84, the ECU 62, the transceiver 66, the capacitive sensing array 70, andso forth.

The outer casing 520 is generally rectangular-shaped and has two shorttop and bottom walls 524, 526, respectively, and two long side walls528, 530. The antenna 18 is connected at its base to a top surface 532of the outer casing 520 via a connector 536 to permit the device 514 tocommunicate with the system 16.

The outer casing 520 includes a plurality of mounting arms 540 that arepositioned along the walls 526, 528, 530. Each mounting arm 540 is apossible attachment point for the support leg 522. Each arm 540 includesa plurality of posts 544, 546, 548 that extend outwardly from each ofthe walls 526, 528, 530. A rod 550 extends between the posts 544, 546,548. In the illustrative embodiment, the rod 550 has a cylindricalcross-section, but it should be appreciated that in other embodiments itmay have a different cross-section.

As shown in FIG. 14, the support leg 522 includes a rear panel 560 thatis connected to a foot panel 562. The rear panel 560 has a pair of clips564 that extend outwardly from its back surface 566. Each clip 564includes teeth 568 that engage the rod 550 of a mounting arm 540 tosecure the support leg 522 to the pest control device 514. In theillustrative embodiment, the clips 564 are configured to engage the rod550 such that the support leg 522 is hinged to the pest control device514 and may pivot relative to the outer casing 522.

The foot panel 562 includes an upper surface 570 configured to bepositioned below the trap 516 and a lower surface 572 positionedopposite the surface 570. In the illustrative embodiment, the surfaces570, 572 are substantially smooth surfaces. In other embodiments, thesurfaces may include grooves, ribs, or other features to grip the trap516. As shown in FIG. 15, an angle α is defined between the foot panel562 and rear panel 560. In the illustrative embodiment, the angle α isgreater than 90 degrees.

The outer casing 520 and support leg 522 are each formed from a hard,durable plastic. In other embodiments, the casing 520 and leg 522 may beformed from any environmentally resistant material.

To set up the trap 516 relative to the control device 514, the trap 516is placed into contact with the upper surface 570 of the support leg522. The weight of the trap 516 forces the support leg 522 to pivotrelative to the outer casing 520 and bring the lower surface 572 of thefoot panel 562 into contact with the ground, as shown in FIG. 12. As thesupport leg 522 pivots, the wall of the outer casing 520 that isattached to the support leg 522, in this case, wall 526, is forcedupward, and the outer casing 520 is positioned at a angle β relative tothe ground. With the trap 516 is placed on the upper surface 570 of leg522, the weight of the trap 516 maintains the control device 514 in theposition shown in FIG. 12.

As shown in FIGS. 16-18, the snap-type rodent trap 516 can be either inan “Armed” condition (FIG. 16) or a “Tripped” condition (FIG. 18). Thetrap 516 includes a base 580 and a generally U-shaped jaw 582 that ispivotally coupled to a spring 584. In the “Armed” condition, the jaw 582is held in place by a trap pin 586 such that the jaw 582 is adjacent tothe pest control device 514, as shown in FIG. 16. In this configuration,if a rodent applies sufficient downward pressure on a bait plate 588,the trap pin 586 is displaced, and the jaw 582 snaps over the bait plate588 to pen the rodent between the jaw 582 and the base 580. In thatposition, the trap 516 is in a “Tripped” condition.

During the transition from the “Armed” condition to “Tripped” condition,the force of the snap causes the trap 516 to be lifted upwardly relativeto the ground thereby releasing the leg 522 of the pest control device514, thereby allowing the leg 522 to pivot as shown in FIGS. 17-18. Asshown in FIG. 18, the outer casing 520 drops to the ground level whenthe trap 516 is lifted off of the leg 522. As described in greaterdetail below, the position sensor 84 monitors this orientation orposition of the outer casing 520 and generates (x, y, z) orientationdata that may be used to detect movement of the outer casing 520. Thesignals are then analyzed by the system 16 to determine the condition ofthe trap 516.

Referring now to FIG. 19, a monitoring routine 600 for monitoring theorientation or position of a pest control device is illustrated. In theillustrative embodiment, the routine 600 is an exemplary subroutine usedin block 104 of FIG. 6 for monitoring environmental sensor array. Itshould be appreciated that in other embodiments the routine may be aseparate routine that may be used as an alternative to the routine 100of FIG. 6. As described in greater detail below, the routine 600 causesthe ECU 62 to monitor the data generated by the position sensor 84 andtake a reading of the (x, y, z) coordinates of the position sensor 84(and hence outer casing 520) at predetermined time intervals. When theECU 62 has taken a predetermined number of readings, the ECU 62 mayprocess the sensor data to determine whether the pest control device 514is stable and determine whether the movement of the pest control device514 exceeds a predetermined angular threshold. Alternatively, in someembodiments, the position sensor 84 may detect the real-time movement ofthe pest control device 514 throughout the transition from the “Armed”condition to “Tripped” condition to monitor the position of the outercasing 520. If sufficient movement data of the pest control device 514is detected, such movement data may be transmitted to the remote system16 to be used to analyze the status of the trap 516.

The routine 600 begins in block 602 in which the ECU 62 determineswhether a predetermined time interval has elapsed since the ECU 62stored its last reading of the sensor data. If the ECU 62 determinesthat the predetermined time interval has not yet been elapsed, themonitoring routine 600 ends. If the ECU 62 determines that thepredetermined time interval has elapsed, the monitoring routine 600proceeds to block 604. It should be appreciated that the predeterminedtime interval may be programmable and may be set based on the nature ofthe rodent and environment surrounding the pest control device 514. Inthe illustrative embodiment, the predetermined time interval is 60seconds.

In block 604, the ECU 62 monitors and records the (x, y, z) coordinatesincluded in the position data generated by the sensor 84. Each sensorreading indicates the orientation or position of the outer casing 520 ofthe pest control device 514. After the ECU 62 has taken a reading of the(x, y, z) coordinates, the monitoring routine 600 may advance to block606. In block 606, the ECU 62 increments a counter and record thatsensor reading before the routine 600 advances to block 608.

In block 608, the ECU 62 determines whether the counter has recorded apredetermined number of sensor readings. When the counter is equal to orgreater than the predetermined number of sensor readings, the routine600 may advance to block 610 to further process the sensor data. Whenthe counter indicates that less than the predetermined number of sensorreadings have been taken, the routine 600 ends. It should be appreciatedthat the predetermined number of sensor readings may be programmable andmay be set based on the nature of the rodent and environment surroundingthe pest control device 514. The illustrative embodiment, thepredetermined number of sensor readings is equal to 8 sensor readings.In other words, the ECU 62 must take 8 sets of (x, y, z,) coordinatesbefore proceeding to block 610; if it has taken less than 8 sets, theroutine 600 ends.

When the routine 600 advances to block 610, the ECU 62 processes thedata recorded during each reading of the predetermined number of sensorreadings. In the illustrative embodiment, the ECU 62 processes the datarecorded by the previous 8 sensor readings. In processing the data, theECU 62 determines the maximum (x_max, y_max, z_max) and minimum (x_min,y_min, z_min) values for each of the x, y, and z coordinates from theprevious 8 sensor readings (i.e., the predetermined number of sensorreadings). The ECU 62 then uses the maximum and minimum values for eachof the x, y, and z coordinates in block 612.

In block 612, the ECU 62 determines whether the outer casing 520 was ina stable orientation or stable position over the predetermined number ofsensor readings. To do so, the ECU 62 calculates the differences betweenthe maximum of each axis (x_max, y_max, z_max) and minimum of each axis(x_min, y_min, z_min) values for each of the x, y, and z coordinates.The maximum of each axis is compared individually against a programmablethreshold for that axis. For example, the difference between x_max andx_min of the 8 sensor readings is compared against a programmablethreshold (x_threshold), the difference between y_max and y_min of the 8sensor readings is compared against a programmable threshold(y_threshold), and the difference between z_max and z_min of the 8sensor readings is compared against a programmable threshold(z_threshold). If all of the differences between the maximum and minimumvalues of the x, y, and z coordinates are less than or equal to thecorresponding programmable thresholds (x_threshold, y_threshold,z_threshold), the routine 600 advances to block 614. If any one of thedifferences is greater than the corresponding programmable thresholds,the routine 600 advances to block 624 in which the counter is resetbefore the routine 600 ends.

The programmable thresholds used in block 612 are set based on, amongother things, the nature of the rodent and environment surrounding thepest control device 514. Ideally, with no physical movement of the outercasing 520, the differences between the maximum and minimum values ofthe x, y, and z coordinates should be at or near zero. However,disruptions from environmental factors, including wind and vibration,may cause the outer casing 520 to move. The programmable thresholds maybe set higher than zero to permit movement of the casing 520 caused bywind and/or vibration. In the illustrative embodiment, each programmablethreshold for the x, y, z coordinates (x_threshold, y_threshold,z_threshold) is set to 50 units, where each unit represents 1/1024th ofthe force of gravity.

In some embodiments, the ECU 62 may add the differences between themaximum (x_max, y_max, z_max) and minimum (x_min, y_min, z_min) valuesand compare the sum of the differences to a net programmable threshold(i.e., the sum of x_threshold, y_threshold, and z_threshold).

As described above, if the difference between the maximum and minimumvalues of the x, y, and z coordinates is less than or equal to theprogrammable threshold, the routine 600 may advance to block 614. Inblock 614, the ECU 62 calculates average values for the x, y, and zcoordinates recorded during the predetermined number of sensor readings.In other words, the ECU 62 calculates average x, y, and z coordinatevalues taken during the previous 8 sensor readings. The ECU 62 thenstores the average x, y, and z coordinate values as new stableorientation values A_(x), A_(y), and A_(z), and the routine 600 mayadvance to block 616.

In block 616, the ECU 62 calculates the deflection angle between the newstable orientation values and the previous stable orientation values. Todo so, the ECU 62 recalls from memory the previous stable orientationvalues B_(x), B_(y), and B_(z). The ECU 62 may then calculate adeflection angle between the new and previous stable orientations usingEquation (3) below.

$\begin{matrix}{{DeflectionAngle} = {\cos^{- 1}\left( \frac{\left( {A_{X}*B_{X}} \right) + \left( {A_{Y}*B_{Y}} \right) + \left( {A_{Z}*B_{Z}} \right)}{\sqrt{\left( {A_{X}^{2} + A_{Y}^{2} + A_{Z}^{2}} \right)*\left( {B_{X}^{2} + B_{Y}^{2} + B_{Z}^{2}} \right)}} \right)}} & (3)\end{matrix}$

A_(x), A_(y), A_(z) are the coordinates of new stable orientation, andB_(x), B_(y), B_(z) are the coordinates of previous stable orientation.

Subsequent to calculating the deflection angle between the new andprevious stable orientations, the ECU 62 proceeds to block 618 in whichthe ECU 62 determines whether the calculated deflection angle is greaterthan a predetermined angular threshold. In the illustrative embodiment,the predetermined angular threshold is equal to 2.5 degrees. Thepredetermined angular threshold is a predetermined minimum deflectionangle to prevent false positive readings by eliminating insignificantchanges in orientation caused by the environment surrounding. Thepredetermined angular threshold is programmable and is determined basedon, among other things, the environment surrounding the pest controldevice 514. It should be appreciated that in other embodiments thepredetermined angular threshold may be different from 2.5 degrees.

If the ECU 62 determines that the deflection angle is less than or equalto the predetermined angular threshold, the ECU 62 concludes that theorientation change in the pest control device 514 is insignificant andproceeds to block 622. In block 622, the ECU 62 updates the previousstable orientation readings B_(x), B_(y), and B_(z) with the new stableorientation readings A_(x), A_(y), and A_(z) before advancing to block624 in which the ECU 62 resets the counter and proceeds to end themonitoring routine 600.

If the ECU 62 determines that the deflection angle is greater than thepredetermined angular threshold, the routine 600 advances to block 620.In block 620, the ECU 62 sends a message to the system 16 to inform thesystem 16 that the deflection angle exceeded the predetermined angularthreshold. The system 16 may then use that information to determine thestatus of the trap 516 and inform the operator. For example, during aninitial set up of the trap when some movements of the pest controldevice 514 are expected due to the human activities, the system 16 setsa default status of the trap 516 as “Trapped.” When the trap 516 isproperly positioned and is stable, the ECU 62 stores an initialorientation of the trap and sends the message to the system 16 that thedeflection angle exceeded the predetermined angular threshold. Thesystem 16 then updates the status of the trap 516 to “Armed.”Subsequently, when the system 16 receives the following message that thedeflection angle exceeded the predetermined angular threshold, thesystem 16 updates the status of the trap 516 to “Tripped” and alerts theoperator that the trap 516 has been tripped. The routine 600 may thenadvance to block 622 and subsequently to block 624 as described above.

Referring now to FIGS. 20-31, other embodiments of a pest control deviceare shown. The embodiments of FIGS. 20-31 include many of the samefeatures described above in regard to FIGS. 12-18. The same referencenumbers are used in FIGS. 20-31 to identify features that are the sameor similar to those described above in regard to the embodiments ofFIGS. 1-19. As shown in FIGS. 20-31, the pest control devices 714, 814,914 may be separately coupled to a snap-type rodent trap 516; however,the coupling mechanism may vary between different embodiments as will bedescribed in detail below.

In the embodiments of FIGS. 20-31, the electrical components 54 of thedevices 714, 814, 914 are the same or similar to the electricalcomponents of the devices 14, 514 including the position sensor 84, theECU 62, the transceiver 66, the capacitive sensing array 70, and soforth. In operation, the position sensor 84 of each pest control devices714, 814, 914 is operable to detect movement of its respective pestcontrol device 714, 814, 914 and provide an indication of whether thetrap 516 has been activated, as described in greater detail below.Similar to the position sensor 84 described above in regard to theembodiments of FIGS. 1-19, the position sensor 84 is a 3-axis digitalaccelerometer such as, for example, the MMA8652, which is commerciallyavailable from Freescale.

Referring now to FIGS. 20-23, the pest control device 714 is coupled tothe snap-type rodent trap 516 via integrated clips 722 of the pestcontrol device 714. Accordingly, the pest control device 714 includes anouter casing 720 and the pair of clips 722 attached to the outer casing720. The outer casing 720, like the casing 520 described above in regardto FIGS. 11-19, houses and protects the electrical components 54 fromenvironmental factors, including water ingress, dust, dirt, leaves,humidity, and waste.

As shown in FIG. 20, the outer casing 720 is generallyrectangular-shaped and has two short top and bottom walls 724, 726,respectively, and two long side walls 728, 730. The antenna 18 isconnected at its base to the top surface 732 of the outer casing 720 viathe connector 536 to permit the device 714 to communicate with thesystem 16. The outer casing 720 further includes the pair of clips 722that extends outwardly from the top wall 724 of the outer casing 720.Each clip 722 includes teeth 734 that engage a center wire 590 of thegenerally U-shaped jaw 582 of the trap 516 to secure the outer casing720 to the trap 516. To set up the trap 516 relative to the controldevice 714, the clips 722 of the outer casing 720 engage the center wire590 of the jaw 582 of the trap 516 such that the outer casing 720 ishinged to the jaw 582 of the trap 516 and may pivot relative to the trap516.

As shown in FIGS. 21-23, the snap-type rodent trap 516 can be either inthe “Armed” condition (FIG. 21) or the “Tripped” condition (FIG. 23). Inthe “Armed” condition, the jaw 582 is held in place by the trap pin 586and the outer casing 720 is laterally attached to the trap 516 such thatthe top wall 724 of the outer casing 720 that is attached to the trap516 is forced upward, and the outer casing 720 is positioned at a angleβ relative to the ground. During the transition from the “Armed”condition to “Tripped” condition, the jaw 582 snaps over the bait plate588 to pen the rodent between the jaw 582 and the base 580 of the trap516. As the jaw 582 snaps over the bait plate 588, the control device714 is lifted upwardly with the jaw 582 relative to the ground whileallowing the clips 722 of the outer casing 720 to pivot as shown inFIGS. 21-23. The jaw 582 and the outer casing 720 then drop relative tothe ground causing the trap 516 to be in “Tripped” condition. Theposition sensor 84 monitors this orientation of the outer casing 720 andgenerates (x, y, z) position data that may be used to detect movement ofthe outer casing 720.

A routine, similar to the routine 600 described above in regard to FIGS.12-19, causes the ECU 62 to monitor the data generated by the positionsensor 84 and take a reading of the (x, y, z) coordinates of theposition sensor 84 (and hence outer casing 720) at predetermined timeintervals. When the ECU 62 has taken a predetermined number of readings,the ECU 62 may process the sensor data to determine whether the pestcontrol device 714 is stable and determine whether the movement of thepest control device 714 exceeds a predetermined angular threshold. Thesignals are then analyzed by the system 16 to determine the condition ofthe trap 516. Alternatively, in some embodiments, the position sensor 84may detect the real-time movement of the pest control device 714throughout the transition from the “Armed” condition to “Tripped”condition to monitor the position of the outer casing 720.

Referring now to FIGS. 24-27, the pest control device 814 is coupled tothe snap-type rodent trap 516 via integrated arms 822 of the pestcontrol device 814. Accordingly, the outer casing 820 of the controldevice 814 includes a pair of generally L-shaped arms 822 attached tothe outer casing 820. The outer casing 820, like the casing 520, 720described above in regard to FIGS. 11-23, houses and protects theelectrical components 54 from environmental factors, including wateringress, dust, dirt, leaves, humidity, and waste.

As shown in FIG. 24, the outer casing 820 is generallyrectangular-shaped and has two short top and bottom walls 824, 826,respectively, and two long side walls 828, 830. The antenna 18 isconnected at its base to the top surface 832 of the outer casing 820 viathe connector 536 to permit the device 814 to communicate with thesystem 16. The outer casing 820 further includes the pair of arms 822that extends outwardly from the bottom wall 826 of the outer casing 820.Each arm 822 includes a first member 834 extends outwardly from thebottom wall 826 of the outer casing 820 and is connected to a secondmember 836. The second member 836 is bent downwardly toward the ground,forming a generally L-shape relative to the first member 834.

To set up the control device 814 relative to the trap 516, the arms 822of the outer casing 820 are placed over the center wire 590 of the jaw582 of the trap 516 such that the second members 826 of the arms 822engage the base 580 of the trap 516. Thus, in the “Armed” conditionshown in FIGS. 24-25, the control device 814 is placed relative to thetrap 516 such that the center wire 590 of the jaw 582 is placed within agroove between the second members 836 of the arms 822 and the bottomwall 826 of the outer casing 820 and between the first members 834 ofthe arms 822 and the base 580 of the trap 516. In this configuration,the outer casing 820 is positioned at a angle β relative to the ground,and the arms 822 of the control device 814 do not make direct physicalcontact with the jaw 582 of the trap 516.

During the transition from the “Armed” condition to “Tripped” conditionas shown in FIGS. 25-27, the jaw 582 snaps over the bait plate 588 topen the rodent between the jaw 582 and the base 580 of the trap 516. Asthe jaw 582 started to snap, the center wire 590 of the jaw 582 engagesthe L-shaped arms 822 of the outer casing 820 causing the control device814 to be lifted upwardly relative to the ground, as shown in FIG. 26.When the center wire 590 of the jaw 582 passes an imaginary line 594orthogonal to the base 580 of the trap 516, the center wire 590 of thejaw 582 drags the second member 826 of L-shaped arms 822 and the forceof the snap throws the control device 814 away from the center wire 590,as shown in FIG. 26. The position sensor 84 monitors this orientation ofthe outer casing 820 and generates (x, y, z) position data that may beused to detect movement of the outer casing 820.

A routine, similar to the routine 600 described above in regard to FIGS.12-19, causes the ECU 62 to monitor the data generated by the positionsensor 84 and take a reading of the (x, y, z) coordinates of theposition sensor 84 (and hence outer casing 820) at predetermined timeintervals. When the ECU 62 has taken a predetermined number of readings,the ECU 62 may process the sensor data to determine whether the pestcontrol device 814 is stable and determine whether the movement of thepest control device 814 exceeds a predetermined angular threshold. Thesignals are then analyzed by the system 16 to determine the condition ofthe trap 516. Alternatively, in some embodiments, the position sensor 84may detect the real-time movement of the pest control device 814throughout the transition from the “Armed” condition to “Tripped”condition to monitor the position of the outer casing 820.

Referring now to FIGS. 28-31, the pest control device 914 is coupled tothe snap-type rodent trap 516 via an integrated channel 922 of the pestcontrol device 914. The outer casing 920, like the casing 520, 720, 820described above in regard to FIGS. 11-27, houses and protects theelectrical components 54 from environmental factors, including wateringress, dust, dirt, leaves, humidity, and waste.

As shown in FIG. 28, the outer casing 920 is generallyrectangular-shaped and has two short top and bottom walls 924, 926,respectively, and two long side walls 928, 930. The antenna 18 isconnected at its base to the top surface 932 of the outer casing 920 viathe connector 536 to permit the device 914 to communicate with thesystem 16. The outer casing 920 of the control device 914 furtherincludes a channel 922. The channel 922 is defined in the bottom surface934 of the outer casing 920 and extends from one sidewall 928 to theopposite sidewall 530 near the bottom wall 926 of the outer casing 920.The channel 922 is configured to receive the center wire 590 of the jaw582 of the trap 516, as shown in FIG. 28. When the control device 914 isset relative to the trap 516, the center wire 590 is received in thechannel 922 causing the outer casing 520 to be positioned at an angle βrelative to the ground.

In the “Armed” condition shown in FIGS. 28-29, the control device 914 isplaced relative to the trap 516 such that the center wire 590 of the jaw582 of the trap 516 engages the channel 922 of the outer casing 920.During the transition from the “Armed” condition to “Tripped” conditionas shown in FIGS. 29-31, the jaw 582 snaps over the bait plate 588. Asthe jaw 582 started to snap, the center wire 590 of the jaw 582 remainsin the channel 922 of the outer casing 920 lifting the control device914 upwardly relative to the ground, as shown in FIG. 30. When thecenter wire 590 of the jaw 582 passes an imaginary line 594 orthogonalto the base 580 of the trap 516, force of the snap further lifts thecontrol device 914 and pushes it outwardly away from trap 516, therebyflipping the control device 914, as shown in FIG. 31. The positionsensor 84 monitors this orientation of the outer casing 920 andgenerates (x, y, z) position data that may be used to detect movement ofthe outer casing 920.

A routine, similar to the routine 600 described above in regard to FIGS.12-19, causes the ECU 62 to monitor the data generated by the positionsensor 84 and take a reading of the (x, y, z) coordinates of theposition sensor 84 (and hence outer casing 920) at predetermined timeintervals. When the ECU 62 has taken a predetermined number of readings,the ECU 62 may process the sensor data to determine whether the pestcontrol device 914 is stable and determine whether the movement of thepest control device 914 exceeds a predetermined angular threshold. Thesignals are then analyzed by the system 16 to determine the condition ofthe trap 516. Alternatively, in some embodiments, the position sensor 84may detect the real-time movement of the pest control device 814throughout the transition from the “Armed” condition to “Tripped”condition to monitor the position of the outer casing 920.

Referring now to FIG. 32, the pest control device 1014, same or similarto FIG. 1-19, is mounted on a tomcat snap trap 1016. As shown in FIG.32, the outer casing 1020 is generally rectangular-shaped and has twoshort top and bottom walls 1024, 1026, respectively, and two long sidewalls 1028, 1030. The antenna 18 is connected at its base to the topsurface 1032 of the outer casing 1020 via the connector 536 to permitthe device 1014 to communicate with the system 16.

The tomcat snap trap 1016 includes a base 1038 and a pivoting member1040 pivotally coupled to a biasing member 1042. The pivoting member1040 includes a flat top surface 1044. The outer casing 1020 of the pestcontrol device 1014 is mounted on the top surface 1044 of the snap trap1016 by a fastener 1036. In the “Armed” condition, the pivoting member1040 is held in place by the biasing member 1042. In this configuration,if a rodent applies sufficient downward pressure on a bait plate 1034,the biasing member 1042 is displaced, and the pivoting member 1040 fallson the bait plate 1034 to pen the rodent between the pivoting member1040 and the base 1038. During the transition from the “Armed” conditionto “Tripped” condition, the control device 1014 moves with the pivotingmember 1040. In the illustrative embodiment, the movement of thepivoting member 1040 represents the movement of the control device 1014.The position sensor 84 monitors this orientation of the outer casing1020 and generates (x, y, z) position data that may be used to detectmovement of the outer casing 1020.

A routine, similar to the routine 600 described above in regard to FIGS.12-19, causes the ECU 62 to monitor the data generated by the positionsensor 84 and take a reading of the (x, y, z) coordinates of theposition sensor 84 (and hence outer casing 820) at predetermined timeintervals. When the ECU 62 has taken a predetermined number of readings,the ECU 62 may process the sensor data to determine whether the pestcontrol device 1014 is stable and determine whether the movement of thepest control device 1014 exceeds a predetermined angular threshold. Thesignals are then analyzed by the system 16 to determine the condition ofthe trap 516. Alternatively, in some embodiments, the position sensor 84may detect the real-time movement of the pest control device 814throughout the transition from the “Armed” condition to “Tripped”condition to monitor the position of the outer casing 1020.

Referring now to FIG. 33, a monitoring routine 1200 for monitoring theorientation or position of any of the pest control devices describedherein is illustrated. In the illustrative embodiment, the routine 1200is an exemplary subroutine used in block 104 of FIG. 6 for monitoringenvironmental sensor array. It should be appreciated that in otherembodiments the routine may be a separate routine that may be used as analternative to the routine 100 of FIG. 6 or the routine 600 of FIG. 19.Some of the blocks of the routine 1200 are similar to the blocks of theroutine 600, and the same reference numbers will be used to identifysuch blocks in FIG. 33. Similar to the routine 600, the routine 1200causes the ECU 62 to monitor the data generated by the position ororientation sensor 84 and take a reading of the (x, y, z) coordinates ofthe position sensor 84 (and hence outer casing) at predetermined timeintervals. When the ECU 62 has taken a predetermined number of readings,the ECU 62 may process the sensor data to determine whether the pestcontrol device is stable and determine whether the movement of the pestcontrol device exceeds a predetermined threshold.

The routine 1200 begins in block 602 in which the ECU 62 determineswhether a predetermined time interval has elapsed since the ECU 62stored its last reading of the sensor data. If the ECU 62 determinesthat the predetermined time interval has not yet been elapsed, themonitoring routine 1200 ends. If the ECU 62 determines that thepredetermined time interval has elapsed, the monitoring routine 1200proceeds to block 1204. It should be appreciated that the predeterminedtime interval may be programmable and may be set based on the nature ofthe rodent and environment surrounding the pest control device 514. Theillustrative embodiment, the predetermined time interval is 60 seconds.

In block 1204, the ECU 62 monitors and records the (x, y, z) coordinatesincluded in the position data generated by the sensor 84. In theillustrative embodiment, the (x, y, z) coordinates form an orientationvalue that indicates the orientation or position of the outer casing ofthe pest control device. In the routine 1200, the ECU 62 identifies theoldest stored orientation value (i.e., the oldest reading of (x, y, z)coordinates stored in memory) and replaces the oldest orientation valuewith the new (x, y, z) coordinates of the current reading.Illustratively, the ECU 62 stores only 8 sets of (x, y, z) coordinates,and the new (x, y, z) coordinates of the current reading replace one ofthose sets. It should be appreciated that in other embodiments the ECUmay be configured to store additional or fewer sets of (x, y, z)coordinates (i.e., additional orientations values).

In the illustrative embodiment, a counter is used to index the stored(x, y, z) coordinates so that the ECU 62 may identify which set is theoldest set. At the conclusion block 1204, the routine 1200 may advanceto block 1206 in which the counter is incremented to correspond to thenext stored set of (x, y, z) coordinates, which is now the oldest set of(x, y, z) coordinates in memory. It should be appreciated that othersoftware tools may be used to identify the oldest set of (x, y, z)coordinates. The routine 1200 may advance to block 610.

When the routine 600 advances to block 610, the ECU 62 processes the 8sets of (x, y, z) coordinates to determine the maximum (x_max, y_max,z_max) and minimum (x_min, y_min, z_min) values for each of the x, y,and z coordinates of the 8 sets of (x, y, z) coordinates stored inmemory. The ECU 62 may then use the maximum and minimum values for eachof the x, y, and z coordinates in block 612.

In block 612, the ECU 62 determines whether the pest control device wasin a stable orientation or stable position over the predetermined numberof sensor readings. To do so, the ECU 62 calculates the differencesbetween the maximum of each axis (x_max, y_max, z_max) and minimum ofeach axis (x_min, y_min, z_min) values for each of the x, y, and zcoordinates. The maximum of each axis is compared individually against aprogrammable threshold for that axis. If all of the differences betweenthe maximum and minimum values of the x, y, and z coordinates are lessthan or equal to the corresponding programmable thresholds (x_threshold,y_threshold, z_threshold), the routine 1200 may advance to block 614. Ifany one of the differences is greater than the correspondingprogrammable thresholds, the routine 1200 ends.

In block 614, the ECU 62 calculates average values for the x, y, and zcoordinates recorded during the predetermined number of sensor readings.In other words, the ECU 62 calculates average x, y, and z coordinatevalues taken during the previous 8 sensor readings. The ECU 62 thenstores the average x, y, and z coordinate values as new stableorientation values A_(x), A_(y), and A_(z), and the routine 600 mayadvance to block 616. In block 616, the ECU 62 calculates the deflectionangle between the new stable orientation values and the previous stableorientation values, as described above in regard to FIG. 19.

Subsequent to calculating the deflection angle between the new andprevious stable orientations, the ECU 62 proceeds to block 618 in whichthe ECU 62 determines whether the calculated deflection angle is greaterthan a predetermined angular threshold. In the illustrative embodiment,the predetermined angular threshold is equal to 2.5 degrees, which is apredetermined minimum deflection angle to prevent false positivereadings by eliminating insignificant changes in orientation caused bythe environment surrounding. It should be appreciated that in otherembodiments the predetermined angular threshold may be different from2.5 degrees.

If the ECU 62 determines that the deflection angle is less than or equalto the predetermined angular threshold, the ECU 62 concludes that theorientation change in the pest control device 514 is insignificant andmay proceed to block 622. In block 622, the ECU 62 updates the previousstable orientation readings B_(x), B_(y), and B_(z) with the new stableorientation readings A_(x), A_(y), and A_(z) before the monitoringroutine 600 ends.

If the ECU 62 determines that the deflection angle is greater than thepredetermined angular threshold, the routine 1200 advances to block 620.In block 620, the ECU 62 sends a message to the system 16 to inform thesystem 16 that the deflection angle exceeded the predetermined angularthreshold. The system 16 may then use that information to determine thestatus of the trap 516 and inform the operator, as described above inregard to FIG. 19. The routine 600 may then advance to block 622 inwhich the ECU 62 updates the previous stable orientation readings B_(x),B_(y), and B_(z) with the new stable orientation readings A_(x), A_(y),and A_(z) before the monitoring routine 600 ends.

In some embodiments, the routines may include one or more subroutines toaccommodate human activity and eliminate false pest detection events,which may occur due to a service provider or installer needing to handlethe pest control device or trap. In one embodiment, the installer orother operator may activate a subroutine in which all sensed activity isignored for a programmable time interval to permit the installer toposition the pest control device and/or trap in a desired location andorientation. Similarly, the routines may include a subroutine in whichall sensed activity is ignored for a programmable time interval topermit a service provider to re-install the pest control device and/ortrap in the desired location and orientation following a service event.It should be appreciated that the programmable time intervals may be thesame or may be separately programmed.

The routines may also include another sub-routine in which sensor datais buffered for a programmable time interval prior to a service event.This may be accomplished using a number of data buckets. Each bucket maybe filled for ¼ of the pre-service time interval. The oldest bucket maybe counted, emptied, and filled with new sensor data if no service eventoccurs during the pre-service time interval. If a service event occursduring the pre-service time interval, all sensor data included in thebuckets may be discarded. It should be appreciated that the pest controlsystem may utilize any combination of the sub-routines described above.

In some embodiments, the position or orientation sensor may be aseparate movable component of the pest control device. In suchembodiments, the orientation sensor may be directly coupled to the pesttrap device. For example, the pest trap device may be a cage including ahousing, a trap door pivotally attached to the housing, and a biasingmember connecting the door and the housing. In some embodiments, baitmay be deposited into the cage to lure the rodents into the cage. Theposition or orientation sensor of the pest control device may be coupledto the trap door to monitor movement of the trap door. The pest controldevice may be inside or outside of the housing of the pest trap device.In the “Armed” condition, the trap door of the pest trap device may beopen, creating an entrance path into the cage. When a pest/rodent entersthe cage, the pest/rodent may trigger the biasing member to close thetrap door, thereby entrapping the rodent and setting the cage in the“Tripped” condition. During this transition from the “Armed” conditionto “Tripped” condition, the orientation sensor moves with the trap door.The orientation sensor monitors the orientation of the trap door togenerate (x, y, z) position data.

A routine, similar to the routine 600 described above in regard to FIGS.12-19, may cause the ECU 62 to monitor the data generated by theorientation sensor and take a reading of the (x, y, z) coordinatesgenerated by the orientation sensor at predetermined time intervals.When the ECU 62 has taken a predetermined number of readings, the ECU 62may process the sensor data to determine whether the trap door is stableand determine whether the movement of the trap door exceeds apredetermined angular threshold. The signals are then analyzed by thesystem 16 to determine the condition of the cage. Alternatively, in someembodiments, the orientation sensor may detect the real-time movement ofthe trap door throughout the transition from the “Armed” condition to“Tripped” condition to monitor the position of the cage.

The pest control device 14 may be used in conjunction with other pestcontrol devices 14 to monitor a site. To do so, the pest control devices14 may be positioned at various locations throughout a building or otherfacility. Optional repeaters incorporating two-way transceivers may beused to extend the range of communications between the devices 14.Additionally, a gateway device incorporating a two-way transceiver forcommunicating with the devices 14 and/or repeaters and the remote system16. The gateway device may incorporate digital cellular technology topermit it to communicate with the remote system 16. An exemplary systemof repeaters and gateway devices is shown and described in U.S. Pat. No.8,026,822, which issued Sep. 8, 2009 and is expressly incorporatedherein by reference.

While the disclosure has been illustrated and described in detail in thedrawings and foregoing description, such an illustration and descriptionis to be considered as exemplary and not restrictive in character, itbeing understood that only illustrative embodiments have been shown anddescribed and that all changes and modifications that come within thespirit of the disclosure are desired to be protected.

There is a plurality of advantages of the present disclosure arisingfrom the various features of the method, apparatus, and system describedherein. It will be noted that alternative embodiments of the method,apparatus, and system of the present disclosure may not include all ofthe features described yet still benefit from at least some of theadvantages of such features. Those of ordinary skill in the art mayreadily devise their own implementations of the method, apparatus, andsystem that incorporate one or more of the features of the presentinvention and fall within the spirit and scope of the present disclosureas defined by the appended claims.

The invention claimed is:
 1. A pest control device comprising: acapacitive sensor array including a plurality of sensor pads, thecapacitive sensor array being configured to generate an electricaloutput signal indicating the state of each sensor pad, and an electroniccontroller electrically connected to the capacitive sensor array,wherein the electronic controller is configured to: receive theelectrical output signals from the capacitive sensor array, determine ameasured capacitance value for each sensor pad based on each electricaloutput signal, determine whether a difference between a measuredcapacitance value of at least one sensor pad and a correspondingbaseline exceeds a first predetermined threshold, determine whether thedifference between the measured capacitance value of the at least onesensor pad exceeds a second predetermined threshold, update a counterwhen the difference exceeds the first predetermined threshold and doesnot exceed the second predetermined threshold, and record a first eventindicative of a presence of a pest when the counter exceeds apredetermined limit.
 2. The pest control device of claim 1, wherein theelectronic controller is further configured the calculate a baseline foreach sensor pad based on the measured capacitance value of the sensorpad.
 3. The pest control device of claim 2, wherein the electroniccontroller is configured to calculate each baseline using the followingequations:${A({new})} = {{A({old})} - {{A({old})}*\left( \frac{Kf}{2^{16}} \right)} + {Cmeas}}$${Baseline} = {{A({new})}*\left( \frac{Kf}{2^{16}} \right)}$ wherein“Kf” is a parameter stored in a memory device of the electroniccontroller, “Cmeas” is the measured capacitance value corresponding tothe electrical output signal of one sensor pad, and “A(old)” is avariable stored in memory.
 4. The pest control device of claim 3,wherein the electronic controller is configured to receive values of Kffrom a remote system.
 5. The pest control device of claim 1, wherein theelectronic controller is configured to record a second event when theelectrical output signals indicate a presence of a human.
 6. The pestcontrol device of claim 5, wherein the electronic controller is furtherconfigured to: determine a sequence of sensor pad contacts based on theelectrical output signals, compare the sequence of sensor pad contactsto a predetermined sequence, and record the second event when thesequence of sensor pad contacts matches the predetermined sequence. 7.The pest control device of claim 6, further comprising a first visualindicator electrically connected to the electronic controller, whereinthe electronic controller is configured to energize the first visualindicator when the sequence of sensor pad contacts matches thepredetermined sequence.
 8. The pest control device of claim 7, furthercomprising a second visual indicator electrically connected to theelectronic controller, wherein the electronic controller is configuredto energize the first visual indicator and the second visual indicatorwhen the electrical output signals indicate the presence of the pest. 9.The pest control device of claim 1, wherein the electronic controller isfurther configured to: determine a sequence of sensor pad contacts basedon the electrical output signals when the difference is greater than thesecond predetermined threshold, compare the sequence of sensor padcontacts to a predetermined sequence, and record a second event when thesequence of sensor pad contacts matches the predetermined sequence. 10.One or more non-transitory, machine readable media comprising aplurality of instructions that when executed cause a pest control deviceto: receive electrical output signals generated by a capacitive sensorarray of the pest control device, wherein the capacitive sensor arrayincludes a plurality of sensor pads, and wherein the electrical outputsignals are indicative of the state of each sensor pad, determine ameasured capacitance value for each sensor pad based on each electricaloutput signal, determine whether a difference between a measuredcapacitance value of at least one sensor pad and a correspondingbaseline exceeds a first predetermined threshold, determine whether thedifference between the measured capacitance value of the at least onesensor pad exceeds a second predetermined threshold, update a counterwhen the difference exceeds the first predetermined threshold and doesnot exceed the second predetermined threshold, and record a first eventindicative of a presence of a pest when the counter exceeds apredetermined limit.
 11. The one or more non-transitory, machinereadable media of claim 10, further comprising a plurality ofinstructions that when executed cause the pest control device tocalculate a baseline for each sensor pad based on the measuredcapacitance value of the sensor pad.
 12. The one or more non-transitory,machine readable media of claim 11, wherein the plurality ofinstructions further cause the pest control device to calculate eachbaseline using the following equations:${A({new})} = {{A({old})} - {{A({old})}*\left( \frac{Kf}{2^{16}} \right)} + {Cmeas}}$${Baseline} = {{A({new})}*\left( \frac{Kf}{2^{16}} \right)}$ wherein“Kf” is a parameter stored in a memory device of the pest controldevice, “Cmeas” is the measured capacitance value corresponding to theelectrical output signal of one sensor pad, and “A(old)” is a variablestored in memory.
 13. The one or more non-transitory, machine readablemedia of claim 12, wherein the plurality of instructions further causethe pest control device to receive values of Kf from a remote system.14. The one or more non-transitory, machine readable media of claim 10,further comprising a plurality of instructions that when executed causethe pest control device to record a second event when the electricaloutput signals indicate a presence of a human.
 15. The one or morenon-transitory, machine readable media of claim 14, wherein theplurality of instructions further cause the pest control device to:determine a sequence of sensor pad contacts based on the electricaloutput signals, compare the sequence of sensor pad contacts to apredetermined sequence, and record the second event when the sequence ofsensor pad contacts matches the predetermined sequence.
 16. The one ormore non-transitory, machine readable media of claim 15, furthercomprising a plurality of instructions that when executed cause the pestcontrol device to energize a first visual indicator when the sequence ofsensor pad contacts matches the predetermined sequence.
 17. The one ormore non-transitory, machine readable media of claim 16, furthercomprising a plurality of instructions that when executed cause the pestcontrol device to energize the first visual indicator and a secondvisual indicator when the electrical output signals indicate thepresence of the pest.
 18. The one or more non-transitory, machinereadable media of claim 10, wherein the plurality of instructionsfurther cause the pest control device to: determine a sequence of sensorpad contacts based on the electrical output signals when the differenceis greater than the second predetermined threshold, compare the sequenceof sensor pad contacts to a predetermined sequence, and record a secondevent when the sequence of sensor pad contacts matches the predeterminedsequence.